<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel=stylesheet href="http://www.google.com/google.css">
<link rel=stylesheet href="../leftnav.css">
<style>
<!--
body,td,font,p,a{font-family:arial,sans-serif}
.i { margin-left: 1em; margin-right: 2em; }
//.style1 {font-weight: bold}
.style1 {font-weight: bold}
.d {color:#999999;text-decoration:italics;font-size:10px;}
.changes {color: #FF0000}
-->
</style>
<script
  src=" https://ssl.google-analytics.com/urchin.js "
  type="text/javascript">
</script>
<script type="text/javascript">
  _uacct="UA-18009-2";
  _utcp="/webmasters/sitemaps/";
  _uanchor=1; 
  urchinTracker();
</script>

<title>Google Webmaster Tools</title>
</head>
<body class=search bgcolor=#ffffff text=#000000 link=#0000CC vlink=#800080 alink=#ff0000 topmargin=3>
<table width=95% border=0 cellpadding=0 cellspacing=2>
  <tr valign=top>
    <td width=1%><a href=https://www.google.com/webmasters/sitemaps/> <img src=http://www.google.com/images/google_sm.gif border=0 width=143 height=59 alt="Return to Google homepage." hspace=15 vspace=5></a></td>
    <td width=100% valign="middle">
		<table width="100%" border="0" cellspacing="0" cellpadding="0">
		<tr>
		<td><font size="+0"><b>Webmaster Tools</b></font></td>
		</tr>
		<tr>
		<td style="border-bottom:1px solid #999999" height="1"><img width="1" height="1" alt=""></td>
		</tr>
		</table>  	
	</td>
  </tr>
</table>
<table border=0 cellpadding=2 cellspacing=0 width=95%> 
  <tr> 
    <td width="175" valign="top">
		<font size="-1">

    <p class="sidenavlink"><a href="http://www.google.com/webmasters/">Webmaster Central</a></p>
    <p class="sidenavlink"><a href="http://sitemaps.org/">Using the Sitemap Protocol</a></p>
    <p class="sidenavtoc">Using the Sitemap Generator</p>

  </font></td>
    <td background=http://www.google.com/images/dot2.gif valign=bottom width=5><img src=http://www.google.com/images/dot2.gif width=1 height=1></td> 
    <td style="background-color: #ffffff" width=10 valign=top><img src=http://www.google.com/images/cleardot.gif width=10 height=1></td> 
    <td>
		<div class="content"> 
      <h1>This sitemap generator is deprecated and no longer supported.</h1>
		
			<p><strong>Contents</strong></p>
			<p><font size="-1"><a href="#before">Before you begin</a>
		    <br><a href="#download">Downloading the Sitemap Generator program files</a>
		    <br><a href="#config">Creating a configuration file</a><br>
		    <a href="#copy">Uploading the files to your web server</a>
		    <br><a href="#execute">Running the Sitemap Generator script</a>
		    <br><a href="#submitting">Submitting your Sitemap to Google</a>
		    <br><a href="#troubleshoot">Troubleshooting</a>
		    </font></p>
			<table border="0" cellpadding="2" cellspacing="0" width="100%"> 
				<tbody><tr> 
				<td style="border-top: 1px solid rgb(221, 173, 8); background-color: rgb(254, 250, 222);"><a name="before"></a><b>Before you begin</b></td> 
				</tr> 
			</tbody></table>
				<p><font size="-1">
The Google Sitemap Generator is a Python script that creates a Sitemap
for your site using the Sitemap Protocol. This script can create
Sitemaps from URL lists, web server directories, or from access logs.
In order to use this script: </font></p>
				
				<ul>
				  <li><font size="-1">You must be able to connect to and run scripts on your web server. </font></li>
				  <li><font size="-1">Your web server must have Python 2.2 or later installed. </font></li>
				  <li><font size="-1">You must know the command that launches Python. (Generally, this is <strong>python</strong>,
but may vary by installation. For instance, if the web server has two
versions of Python installed, the earlier version may be invoked by the
command <strong>python</strong> and the later version may be invoked by the command <strong>python2</strong>.) </font></li>
				  <li><font size="-1">You must know the directory path to your site. If your web server hosts one site, this may be a path such as <strong>var/www/html</strong>. If you have a virtual server that hosts multiple sites, this may be a path such as <strong>home/virtual/site1/fst/var/www/html</strong>. </font></li>
				  <li><font size="-1"> You must be able to upload files to your web server (for instance, using FTP). </font></li>
				  <li><font size="-1">If
you will be generating a list of URLs based on access logs, you must
know the encoding used for those logs and the complete path to them. </font></li>
          </ul>
		  
				<p><font size="-1">If you aren't sure about any of this, you can check with your web hosting company. </font></p>
				<font size="-1">
				<p> Now you&#8217;re ready to get started. Here&#8217;s an overview of what you&#8217;ll need to do. </p>
				</font>
		  <font size="-1">
				<ol>
                  <li><font size="-1"><a href="#download">Download</a> the Sitemap Generator program files. Extract the files to a local directory. </font></li>
                  <li><font size="-1"><a href="#config">Create a configuration file</a> for your site using the provided <strong>example_config.xml</strong> file as a template. Modify this file as needed for your site and save it. </font></li>
                  <li><font size="-1"><a href="#copy">Upload the necessary files</a> to your web server. </font></li>
                  <li><font size="-1"><a href="#execute">Run</a> <strong>sitemap_gen.py</strong>. </font></li>
                  <li><font size="-1"><a href="http://www.google.com/support/webmasters/bin/answer.py?answer=34575&topic=8496">Add</a>  the generated Sitemap to your Google webmaster tools account. </font></li>
		          <li><font size="-1"><a href="#recur">Set up a recurring script</a>. (optional) </font></li>
				</ol>
		  </font>
		  
				<p><font size="-1">If you are unable to use the Sitemap Generator, you can  add a Sitemap to your Google webmaster tools account in <a href=http://www.google.com/support/webmasters/bin/answer.py?answer=34606&topic=8516>another format</a>, such as a simple text file. <a href="http://code.google.com/sm_thirdparty.html">Third-party programs supporting the Sitemap Protocol</a>.</font></p>
				<p><font size="-1"><strong>For News Sitemaps:</strong> The Sitemap Generator is not recommended for use in creating Google News Sitemaps at this time, due to the special requirements of News Sitemaps.  News Sitemaps are intended to be dynamic lists of only the most recently published news articles (rather than the entire website), and they are updated frequently.</font></p>  
				<table border="0" cellpadding="2" cellspacing="0" width="100%"> 
				<tbody><tr> 
				<td style="border-top: 1px solid rgb(221, 173, 8); background-color: rgb(254, 250, 222);"><a name="download"></a><b>1. Downloading the Sitemap Generator program files</b></td> 
				</tr> 
			</tbody></table>
				<font size="-1">
				<p> The Sitemap Generator files are available in ZIP and GZ archive formats <font size="-1">from the following location:</font></p>
				</font>
				<p><font size="-1"><a href="http://www.sourceforge.net/project/showfiles.php?group_id=137793&amp;package_id=153422">http://sourceforge.net/project/showfiles.php?group_id=137793&amp;package_id=153422</a></font></p>
				<font size="-1">
				<p>Once you download the archive, extract it into a local directory. Locate the following files: </p>
				<ul>
                  <li><strong> README</strong> &#8212;contains the latest information about this tool </li>
                  <li><strong> sitemap_gen.py</strong> &#8212;the python script that generates your Sitemap </li>
                  <li><strong> example_config.xml</strong> &#8212;the template configuration file you&#8217;ll use to specify the configuration for your site</li>
                  <li><strong> example_urllist.txt</strong> &#8212;the template URL list you can use if you wish to create a Sitemap based on a set of URLs that you specify</li>
		        </ul>
				</font>
			<table border="0" cellpadding="2" cellspacing="0" width="100%"> 
				<tbody><tr> 
				<td style="border-top: 1px solid rgb(221, 173, 8); background-color: rgb(254, 250, 222);"><a name="config"></a><b>2a. Creating a configuration file</b></td> 
				</tr> 
			</tbody></table>
		  <font size="-1">
		  </font><p><font size="-1">This section provides step-by-step instructions for creating a configuration file. It also provides a <a href="#config_reference">complete reference</a> of the options available. If you are creating <a href="http://www.google.com/support/webmasters/bin/answer.py?answer=34627&topic=8493">Mobile Sitemaps</a>, see the <a href="#creating_mobile">additional mobile guidelines</a>.</font></p>
				<font size="-1"><p>In order to create a configuration file for your site, you must have the following information: </p>
				<ul>
                  <li>The base URL for your site (such as <strong>http://www.example.com</strong>/). Ensure that you include the protocol (such as <strong>http://</strong>). For instance, <strong>http://www.google.com</strong> is a valid base url, but <strong>www.google.com</strong> is not. </li>
		
                  <li>The
web server path to the location where you want to store the Sitemap.
Generally, this is the path to the base URL as the Sitemap cannot
contain URLs that are in a higher-level directory from the location of
the Sitemap. When you run the Google Sitemap Generator, it creates the
Sitemap and places it in the location you specify. </li>
		 
                  <li>The
methods you want the Sitemap Generator to use to create your Sitemap.
You can use any combination of methods. The following methods are
available: </li>
		  </ul>
				
		  </font><ol>
<ul>
                    <li><font size="-1"><strong> <a href="#URL">URL</a></strong>
&#8212;list individual URLs in this section of the configuration file, along
with information about each URL. You would generally use this method in
conjunction with another method to manually include additional URLs
that other methods wouldn't pick up. </font></li>
                    <li><font size="-1"><strong><a href="#urllist">URL list</a> </strong>
&#8212;point the configuration file to a text file that contains a list of
URLs. You might want to use this method if this text file already
exists or if you use a script to generate a list of URLs. </font></li>
                    <li><font size="-1"><strong><a href="#directory">Directory paths</a></strong>
&#8212;specify the directory paths for your site and corresponding URLs to
those paths. The Sitemap Generator will create a list of URLs based on
the contents of those directories. You might want to use this method if
your site consists of static HTML files. </font></li>
            <li><font size="-1"><strong> <a href="#logs">Access logs</a></strong>
&#8212;point to the path to your log files. The Sitemap Generator will create
a list of URLs based on the URLs included in the logs. You might want
to use this method if your site consists of dynamic pages. </font></li>
 <li><font size="-1"><strong> <a href="#sitemap">Sitemap</a></strong>
&#8212;point to existing Sitemaps that you have created with the Sitemap Generator. The Sitemap Generator will create a single Sitemap that includes the URLs contained in each Sitemap. You could use this method if you have already created several smaller Sitemaps that you want to combine into one larger Sitemap. </font></li>
            </ul>
		  </ol>
				
		  <font size="-1"><p><b><a name="create_config"></a>Create the configuration file as follows:</b></p>
		  </font>
				<ol>
                 <font size="-1"> <li>Open the <strong>example_config.xml</strong> file in a text editor. Save it as a new file (such as <strong>config.xml</strong> or <strong>mysite_config.xml</strong>).</li> 
                 </font>
				
                 
                 <font size="-1">
                 <li>Locate the site definition section: </li>
                 </font>		  
				
				<pre>&lt;site 
base_url="http://www.example.com/" 
store_into="/var/www/docroot/sitemap.xml.gz"
verbose="1"&gt;
				</pre>				
				
                  <font size="-1"><li>Change the <strong>base_url</strong> value to the URL for your site. </li>
		 
                  <li>Change the <strong>store_into</strong>
value to the path on your web server where you want to store the
Sitemap and the filename you want to use for the Sitemap. Generally, this is the path to the base URL since Google can
only accept URLs that are at the same level as or subdirectories of the
directory that holds the Sitemap. You can specify a relative path from
the directory where you upload the script or a complete path from the
root of your web server. If you upload the script to your base URL
directory, you can simply specify the filename.</li>
                  </font>
                  <font size="-1"></font><font size="-1"><li>Locate the generation method sections that begin with <span class="style1">** MODIFY</span> <span class="style1">or DELETE **</span>. Each of these sections corresponds to a method for generating a Sitemap. </li>
                  <li>Delete the sections for the methods you aren&#8217;t going to use.</li>
                  <li>Follow the instructions below for the methods you are going to use. </li>
                <p><strong> URL<a name="URL"></a></strong></p>
                <p> Locate the following section: </p>
                </font>
                  <pre>&lt;!-- ** MODIFY or DELETE ** 
"url" nodes specify individual URLs to include in the map. &lt;br&gt;

Required attributes: 
href - the URL

Optional attributes: 
lastmod - timestamp of last modification (ISO8601 format) 
changefreq - how often content at this URL is usually updated
priority - value 0.0 to 1.0 of relative importance in your site 
--&gt; 

&lt;url href="http://www.example.com/stats?q=name" /&gt; 
&lt;url 
href="http://www.example.com/stats?q=age" 
lastmod="2004-11-14T01:00:00-07:00" 
changefreq="yearly" 
priority="0.3"
/&gt; </pre>
                  <font size="-1">
                <p>This
  section gives two examples: the first includes only the required
  attribute and the second includes the required attribute as well as the
  optional attributes. </p>
                <p>Use this format for each of the URLs you want to include. The <strong>changefreq</strong>
  attribute gives Google a general idea of how often the URL is updated.
  This helps Google know how often to visit the page for new content. The
  <strong>priority</strong> attribute gives Google information about the
  relative importance of this page compared to the other pages of your
  site. This attribute has no effect on how Google compares your page to
  pages on other sites, it just helps Google know which pages of your
  site that you think are most important. </p>
                  </font>
				<p><font size="-1"><strong> URL list <a name="urllist"></a> </strong></font></p>
				<font size="-1"><p> Locate the following section: </p>
				
			</font>
			<pre>
&lt;!-- ** MODIFY or DELETE **
"urllist" nodes name text files with lists of URLs. 
An example file "example_urllist.txt" is provided. 

Required attributes: 
path - path to the file 

Optional attributes: 
encoding - encoding of the file if not US-ASCII 
--&gt; 
&lt;urllist path="example_urllist.txt" encoding="UTF-8" /&gt; 
				</pre>
				
				<p><font size="-1"> Use this format to point to the path and name of the text file that contains your list of URLs. You can use the provided <strong>example_urllist.txt </strong>file
as a template for that text file. You can specify either a relative or complete path to your web server. For instance, if the Sitemap Generator and <strong>urlist.txt </strong>file are located in the same directory, you can simply specify the filename of the<strong> .txt</strong> file, If you create a text file with an encoding other than
UTF-8, you can use the <strong>encoding</strong> attribute to indicate this encoding. If you have multiple .txt files, you can use wildcards. For instance:</font></p>
				<pre>&lt;urllist path=&quot;example_urllist*.txt&quot; encoding=&quot;UTF-8&quot; /&gt; </pre>
				<p><font size="-1">For each URL you include in the text file, you can specify the last modification date, change frequency, and priority. See the <a href="#urllist_reference">URLlist text file reference section</a> for complete information about the structure of this file.</font>  </p>
				<p><font size="-1"><strong> Directory paths<a name="directory"></a> </strong></font></p>
				<p><font size="-1"> Locate the following section: </font></p>
				
				<pre>
&lt;!-- ** MODIFY or DELETE ** 
"directory" nodes tell the script to walk the file system and 
include all files and directories in the Sitemap.

Required attributes:
path - path to begin walking from 
url - URL equivalent of that path 

Optional attributes:
default_file - name of the index or default file for directory URLs

--&gt; 
 &lt;directory  path=&quot;/var/www/icons&quot;    url=&quot;http://www.example.com/images/&quot; /&gt;<br>  &lt;directory<br>     path=&quot;/var/www/docroot&quot;<br>     url=&quot;http://www.example.com/&quot;<br>    default_file=&quot;index.html&quot;<br>  /&gt;
 </pre>
				
				<p><font size="-1">This
section gives two examples. If all of your pages are contained in
subdirectories of one path, then you only need to include one entry.
However, if you have multiple paths to pages on your site, include an
entry for each. </font></p>
				
				<p><font size="-1">Remember that each URL must begin with the base URL you specified in step 3. For instance, the examples given in the <strong>example_config.xml</strong> file both have URLs that begin with <strong>http://www.example.com/</strong>. Therefore, both URLs are valid. </font></p>
				
				<p><font size="-1">Replace
the example entries with entries for your site. Many sites will only
have one entry that points to the base URL. Ensure that <strong>path</strong> value is the complete path to the directory on your web server. Ensure that the <strong>url</strong> value is the complete URL, including the protocol (such as http) and a trailing slash, if required.</font></p>
				<p><font size="-1">You can use the <strong>default_file</strong> parameter to specify the filename that your server uses as the default page for a directory. In the above example, <strong>/var/www/docroot</strong> resolves to <strong>http://www.example.com/index.html</strong>. You are not required to specify this. However, if you do, the Sitemap Generator will include the page that maps to  each subdirectory only once (rather than list both the directory URL and filename URL) and will use the last modified date of the file (rather than the directory) to extract the lastmod attribute for that page. </font></p>
				<p><font size="-1"><strong> Access logs <a name="logs"></a></strong></font></p>
				<p><font size="-1"> Locate the following section: </font></p>
				
<pre>&lt;!-- ** MODIFY or DELETE **
&quot;accesslog&quot; nodes tell the script to scan webserver log files to
extract URLs on your site.  Both Common Logfile Format (Apache's default 
logfile) and Extended Logfile Format (IIS's default logfile) can be read.
				
Required attributes:
 path - path to the file
Optional attributes:
 encoding - encoding of the file if not US-ASCII
  --&gt;
&lt;accesslog path=&quot;/etc/httpd/logs/access.log&quot; encoding=&quot;UTF-8&quot; /&gt;
&lt;accesslog path=&quot;/etc/httpd/logs/access.log.0&quot; encoding=&quot;UTF-8&quot; /&gt;
&lt;accesslog path=&quot;/etc/httpd/logs/access.log.1.gz&quot; encoding=&quot;UTF-8&quot; /&gt;
</pre>
				 
				<p><font size="-1">This
section gives three examples. You should replace these entries and
include an entry for each log file. Ensure that the path value is the complete
path and filename on your web server. If the log files are not encoded
as US-ASCII or UTF-8, then use the optional <strong>encoding</strong> attribute to <a href="#encoding">specify</a> the encoding. Rather than list each log file, you can use wildcards. For instance, in the above example, you could include the following entry that would include all three log files:</font></p>
<pre>&lt;accesslog path=&quot;/etc/httpd/logs/access.log*&quot; encoding=&quot;UTF-8&quot; /&gt; </pre>
				<p><font size="-1">The
Sitemap Generator assigns priority to URLs it finds in the logs based
on how often each URL is accessed. For instance, a URL that has been
accessed 100 times will be given a higher priority than a URL that has
been accessed twice. The actual priority assignment is relative and
depends on each URL as compared to other URLs in the site.</font></p>
<p><font size="-1"><strong> sitemap <a name="sitemap"></a></strong></font></p>
<p><font size="-1"> Locate the following section: </font></p>
				
<pre> &lt;!-- ** MODIFY or DELETE **<br>    
&quot;sitemap&quot; nodes tell the script to scan other Sitemap files.  This can    
be useful to aggregate the results of multiple runs of this script into
a single Sitemap.
				 
Required attributes:
  path - path to the file
  --&gt;
&lt;sitemap path=&quot;/var/www/docroot/subpath/sitemap.xml&quot; /&gt;</pre>
				 
				<p><font size="-1">This
section gives one example. You should replace this entry and
include an entry for each Sitemap you want to include. Ensure that the path value is the complete
path and filename on your web server.  You can list gzipped Sitemaps as well, as long as they have a .gz extension. Rather than list each Sitemap, you can use wildcards. For instance, the following entry would include any Sitemaps that begin with the word &quot;sitemap&quot; and have an .xml extension:</font></p>
<pre>&lt;sitemap path=&quot;/var/www/docroot/subpath/sitemap*.xml&quot; /&gt; </pre>
				<p><font size="-1">The
Sitemap Generator extracts all URLs and the optional data listed for each URL for every Sitemap you list and creates one Sitemap with this information. At this time, we can't guarantee that this method will work Sitemaps created with tools other than the Sitemap Generator.</font></p>



				<font size="-1"><li>Locate the filter definition section:</li></font>
				  
		 
<pre>&lt;!-- ********************************************************         
FILTERS
				
Filters specify wild-card patterns that the script compares
against all URLs it finds. Filters can be used to exclude
certain URLs from your Sitemap, for instance if you have
hidden content that you hope the search engines don't find.

Filters can be either type=&quot;wildcard&quot;, which means standard
path wildcards (* and ?) are used to compare against URLs,
 or type=&quot;regexp&quot;, which means regular expressions are used
to compare.

Filters are applied in the order specified in this file.
An action=&quot;drop&quot; filter causes exclusion of matching URLs.
An action=&quot;pass&quot; filter causes inclusion of matching URLs,
shortcutting any other later filters that might also match.
If no filter at all matches a URL, the URL will be included.
Together you can build up fairly complex rules.

The default action is &quot;drop&quot;.
The default type is &quot;wildcard&quot;.

You can MODIFY or DELETE these entries as appropriate for
your site. However, unlike above, the example entries in
this section are not contrived and may be useful to you as
they are.
********************************************************* --&gt;

&lt;!-- Exclude URLs that end with a '~' (IE: emacs backup files) --&gt;
&lt;filter action=&quot;drop&quot; type=&quot;wildcard&quot; pattern=&quot;*~&quot; /&gt;

&lt;!-- Exclude URLs within UNIX-style hidden files or directories --&gt;
&lt;filter action=&quot;drop&quot; type=&quot;regexp&quot; pattern=&quot;/\.[^/]*&quot; /&gt;
</pre>
				<p><font size="-1">You
can use filtering to exclude specific URLs from the generated Sitemap.
You might want to do this to create a cleaner list, to reduce redundant
listings, or to keep certain URLs from being indexed. Note that if you
use a <a href="http://www.robotstxt.org/wc/robots.html">robots.txt</a>
file to keep URLs from being indexed, then even if the URLs are
included in your Sitemap, Google will not search or index them. </font></p>
				
				<p><font size="-1">
You can use any or all of the filtering methods. You can delete the
entries you don&#8217;t need and can create additional entries, if desired.
Below are sample usages. </font></p>
				<pre>&lt;filter action=&quot;drop&quot; type=&quot;wildcard&quot; pattern=&quot;*.jpg&quot; /&gt;</pre>
				<p><font size="-1">This filter excludes URLs that end in .jpg. You might want to include a
similar filter if all of your site&#8217;s images are embedded within HTML
pages and should not be accessed as standalone URLs. </font></p>
				<pre>&lt;filter action=&quot;pass&quot; type=&quot;wildcard&quot; pattern=&quot;*.htm*&quot; /&gt;
&lt;filter action=&quot;drop&quot; type=&quot;wildcard&quot; pattern=&quot;*&quot; /&gt;</pre>
				<font size="-1"> This filter includes all .htm* files but excludes everything else.</font><br>
				<br>


				<font size="-1"></font><font size="-1"><li>Once you have made all the changes for your site, save the file.</li></font>
				</ol>
				
				
		        <font size="-1"><a name="config_reference"></a><p><b>Config File Syntax Reference</b></p>
		  </font><font size="-1">
				</font>
		  <p><font size="-1">A
complete explanation of the config file syntax is below. Each tag
begins with a code sample, followed by a description of the attributes.
</font></p>
				
		  <p><font size="-1"><strong><a name="sitetag"></a>site<br>
		  </strong></font><font size="-1">Required tag at the beginning of each config file. </font></p>
		  <pre>&lt;site
base_url="http://www.example.com/"
store_into="/var/www/html/sitemap.xml.gz"
verbose="1"
supress_search_engine_notify="1"
default_encoding="UTF-8"&gt;</pre>
				<br>
				<font size="-1">
				<table border="1" cellpadding="2" cellspacing="0" width="100%">
				
					<tbody><tr>
					<td valign="top" width="19%"><pre>base_url</pre></td>
					<td valign="top" width="6%"><font size="-1">required</font></td>
					<td valign="top" width="75%"><font size="-1">The HTTP path of the base of your website - only URLs that begin with this base can be included in the Sitemap</font></td>
					</tr>
					
					<tr>
					<td valign="top"><pre>store_into</pre></td>
					<td valign="top"><font size="-1">required</font></td>
					<td valign="top"><font size="-1">The
web server path to the desired output file. The script will create this
file - there's no need to create the file before running the script.</font></td>
					</tr> 
					
					<tr>
					<td valign="top"><pre>verbose</pre></td>
					<td valign="top"><font size="-1">optional</font></td>
					<td valign="top"><font size="-1">Enter a number from 0-3, with higher numbers corresponding to increased debug information</font></td>
					</tr>
					
					<tr>
					<td valign="top"><pre>suppress_search_engine_notify</pre></td>
					<td valign="top"><font size="-1">optional</font></td>
					<td valign="top"><font size="-1">D</font><font size="-1">isable search engine notification by entering "1" for testing purposes</font></td>
					</tr>
					
					<tr>
					<td valign="top"><pre>default_encoding</pre></td>
					<td valign="top"><font size="-1">optional</font></td>
					<td valign="top"><font size="-1">Specify a character encoding to be applied to file system paths and URLs</font></td>
					</tr>
				 
		  </tbody></table>
		   </font>
					<font size="-1">
					
				<p></p>
				</font>
					<p><font size="-1"><strong>url<br>
					</strong></font><font size="-1">Optional tag that you can use to list each URL in your site. </font></p>
					<p><pre>&lt;url
href="http://www.example.com/stats?q=age" 
lastmod="2004-11-14T01:00:00-07:00" 
changefreq="yearly" 
priority="0.3"
/&gt; </pre></p><table border="1" cellpadding="2" cellspacing="0" width="100%">
				<tbody><tr>
			<td height="20" valign="top" width="19%"><pre>href</pre></td>
					  <td width="6%" valign="top"><font size="-1">required</font></td>
					<td valign="top" width="75%"><font size="-1">The HTTP path of the base of your website - only URLs that begin with this base can be included in the Sitemap</font></td>
					</tr><tr>
					<td valign="top"><pre>lastmod</pre></td>
					<td valign="top"><font size="-1">optional</font></td>
					<td valign="top"><font size="-1">The time the URL was last modified in <a href="http://www.w3.org/TR/NOTE-datetime">W3C Datetime</a> format (YYYY-MM-DDThh:mm:ss+00:00). 
				You may omit the time portion. Examples:<br>
				&nbsp;&nbsp;"2005-02-21T18:00:15+00:00"<br>
				&nbsp;&nbsp;"2005-02-21"</font></td>
					</tr><tr>
					<td valign="top"><pre>changefreq</pre></td>
					 <td valign="top"><font size="-1">optional</font></td>
					<td valign="top"><font size="-1">The frequency with which the URL is likely to change. This is considered a hint and not a command. 
				The value must be one of "always", "hourly", "daily", "weekly", "monthly", "yearly", or "never".</font></td>
					</tr><tr>
					<td valign="top"><pre>priority</pre></td>
					<td valign="top"><font size="-1">optional</font></td>
					<td valign="top"><font size="-1">The
priority of this page relative to other pages on the same site. The
value is a number between 0.0 and 1.0, where 0.0 is the lowest priority
and 1.0 is the highest priority. The priority can affect the order that
search engines select URLs to explore on your site. Since the priority
is relative, it is only used to select between URLs within your own
site; the priority of your pages will not be compared to the priority
of pages on other sites.</font></td>
					</tr>
		  </tbody></table>
					<p><font size="-1"><b>urllist<br>
					</b></font><font size="-1">Optional tag that you can use to point to a text file that contains a list of the URLs in your site. </font></p>
					<pre>&lt;urllist path="/var/www/html/urllist.txt" encoding="UTF-8" /&gt;</pre>
		  <br>
		<table border="1" cellpadding="2" cellspacing="0" width="100%">
				<tbody><tr>
			<td height="20" valign="top" width="19%"><pre>path</pre></td>
					  <td width="6%" valign="top"><font size="-1">required</font></td>
					<td valign="top" width="75%"><font size="-1">The path and filename of the .txt file. You can specify either a relative or complete path. </font></td>
			</tr><tr>
					<td valign="top"><pre>encoding</pre></td>
					<td valign="top"><font size="-1">optional</font></td>
					<td valign="top"><font size="-1">The encoding of the file, if not UTF-8.</font></td>
					</tr>
		  </tbody></table>
<p><font size="-1"><a name="urllist_reference"></a>The <b>urllist.txt</b> file is a simple text file containing a list of URLs to map. You can also include optional 
				    attributes for each URL. Attributes are entered on the same line as the URL and are separated by a single space. 
				    For example:</font>
          </p>
		  <pre>
http://www.example.com/abc/something
http://www.example.com/abc/xyy.pdf lastmod=2001-12-31T14:05:06+00:00
http://www.example.com/abc/def?x=12&amp;y=23 changefreq=weekly priority=0.3</pre>
				<p>
				<font size="-1">
					
				  </font><table border="1" cellpadding="2" cellspacing="0" width="100%">
				<tbody><tr>
					<td width="19%"  valign="top"><pre>lastmod</pre></td>
					<td valign="top" width="6%"><font size="-1">optional</font></td>
					<td width="75%"  valign="top"><p><font size="-1">The time the URL was last modified in <a href="http://www.w3.org/TR/NOTE-datetime">W3C Datetime</a> format (YYYY-MM-DDThh:mm:ss+00:00). 
				  You may omit the time portion. Examples:</font><font size="-1"><br>
				  <br>
&nbsp;&nbsp;"2005-02-21T18:00:15+00:00"<br>
&nbsp;&nbsp;"2005-02-21"</font></p>
				  </td>
				  </tr><tr>
					<td valign="top"><pre>changefreq</pre></td>
					 <td valign="top"><font size="-1">optional</font></td>
					<td valign="top"><font size="-1"><font size="-1">The frequency with which the URL is likely to change. This is considered a hint and not a command. 
				The value must be one of "always", "hourly", "daily", "weekly", "monthly", "yearly", or "never".</font></font></td>
					</tr><tr>
					<td valign="top"><pre>priority</pre></td>
					<td valign="top"><font size="-1">optional</font></td>
					<td valign="top"><font size="-1">The
priority of this page relative to other pages on the same site. The
value is a number between 0.0 and 1.0, where 0.0 is the lowest priority
and 1.0 is the highest priority. The priority can affect the order that
search engines select URLs to explore on your site. Since the priority
is relative, it is only used to select between URLs within your own
site; the priority of your pages will not be compared to the priority
of pages on other sites.</font></td>
					</tr>
					</tbody></table>
				</p>
		  <font size="-1">
		  </font>
		  <p><font size="-1"><strong>directory<br>
		  </strong></font><font size="-1">Optional
tag that you can use to specify directories in your site so the Sitemap
Generator can create a list of URLs from the files found in those
directories. </font></p>
				<pre>--&gt; 
 &lt;directory  path=&quot;/var/www/icons&quot;    url=&quot;http://www.example.com/images/&quot; /&gt;<br>  &lt;directory<br>     path=&quot;/var/www/docroot&quot;<br>     url=&quot;http://www.example.com/&quot;<br>    default_file=&quot;index.html&quot;<br>  /&gt;
 </pre>
		  <table border="1" cellpadding="2" cellspacing="0" width="100%">
				<tbody><tr>
					<td width="19%" valign="top"><pre>path</pre></td>
					<td valign="top" width="6%"><font size="-1">required</font></td>
					<td width="75%" valign="top"><font size="-1">States the initial path. Sitemap Generator will traverse this directory and all subdirectories</font>.</td>
				  </tr>
					
					<tr>
					<td valign="top"><pre>url</pre></td>
					 <td valign="top"><font size="-1">required</font></td>
					<td valign="top"><font size="-1">Specifies the URL equivalent of the path value.</font></td>
					</tr>
					<tr>
					<td valign="top"><pre>default_file</pre></td>
					 <td valign="top"><font size="-1">optional</font></td>
					 <td valign="top"><font size="-1">Specifies the default file for a directory on the server.</font></td>
					</tr>
		    </tbody></table>
		  </font>
		  <p><font size="-1"><b> accesslog<br>
		  </b>Optional
tag that you can use to specify the path and filename of IIS and Apache-style
access logs so the Sitemap Generator can automatically pick up URLs
from them. </font>
          </p>
		  
		  <pre>&lt;accesslog path="/etc/httpd/logs/access-0.log" encoding="UTF-8"/&gt;</pre>			

<table border="1" cellpadding="2" cellspacing="0" width="100%">
				<tbody><tr>
					<td width="19%" valign="top"><pre>path</pre></td>
					<td valign="top" width="6%"><font size="-1">required</font></td>
					<td width="75%" valign="top"><font size="-1">States the path to the file.</font></td>
		  </tr>
					
					<tr>
					<td valign="top"><pre>encoding</pre></td>
					 <td valign="top"><font size="-1">optional</font></td>
					<td valign="top"><font size="-1">Specifies encoding of the file, if not UTF-8.</font></td>
					</tr>	
		  </tbody></table>
		  
		  
		  <p><font size="-1"><b> sitemap <br>
		  </b>Optional
tag that you can use to specify the path and filename of existing Sitemaps that you have created with the Sitemap Generator. The Sitemap Generator will create a single Sitemap that includes the URLs contained in each Sitemap. </font>
          </p>
		  
		  <pre>&lt;sitemap path=&quot;/var/www/docroot/subpath/sitemap.xml&quot; /&gt;</pre>			

<table border="1" cellpadding="2" cellspacing="0" width="100%">
				<tbody><tr>
					<td width="19%" valign="top"><pre>path</pre></td>
					<td valign="top" width="6%"><font size="-1">required</font></td>
					<td width="75%" valign="top"><font size="-1">States the path to the Sitemap file.</font></td>
		  </tr>	
		  </tbody></table>
		  
		  
		  <p><font size="-1"><strong><a name="filter_examples"></a>filter<br>
		  </strong></font><font size="-1">Optional
tag that you can use to build rules that include or exclude specific
files. Filters are obeyed in the order in which they appear in the
config.xml file. However, intermixing filter entries and input entries
(url, urllist, directory, or accesslog) has no additional effect -
every URL the Sitemap Generator adds to the Sitemap is first compared
against every filter. </font><font size="-1">If no filter matches a URL, the default is to include the URL in the Sitemap.</font></p>
				
				<pre>&lt;filter action="drop" type="wildcard" pattern="*/internal/*" /&gt;</pre>			

<table border="1" cellpadding="2" cellspacing="0" width="100%">
				<tbody><tr>
					<td width="19%" valign="top"><pre>action</pre></td>
					<td valign="top" width="6%"><font size="-1">optional</font></td>
					<td width="75%" valign="top">
				      <font size="-1"><p>The action the filter should take. Valid values are:</p>
					  </font>				      <ul>
					  <li><font size="-1">drop - excludes matching URLs. This is the default action, so if no action is specified, the generator assumes &quot;drop&quot;.</font></li>
					  <li><font size="-1">pass - includes matching URLs.</font></li>
					  </ul>
				      </p></td>
		  </tr>
					
					<tr>
					<td width="19%" valign="top"><pre>type</pre></td>
					<td valign="top" width="6%"><font size="-1">optional</font></td>
					<td width="75%" valign="top"><font size="-1"><p>The type of filtering. Valid values are:</p>
					</font>					  <ul>
					<li><font size="-1">wildcard - standard path wildcards (? and *) are used to compare against URLs. This is the default type, so if no type is specified, the generator assumes &quot;wildcard&quot;.</font></li>
					<li><font size="-1">regexp - regular expressions are used.</font></li>
					  </ul></td>
		  </tr>
				 
<tr>
					<td valign="top"><pre>pattern</pre></td>
					 <td valign="top"><font size="-1">required</font></td>
					 <td valign="top"><font size="-1">Specifies the pattern to match against.</font></td>
		  </tr>
		  </tbody></table>

<font size="-1">
<p><b><a name="encoding"></a>Encodings</b></p>
				
		<p>Files referenced by your configuration file, either URL lists or web server logs, 
				can use encodings other than the default UTF-8. You can specify alternate encodings in config.xml 
				to affect how the Sitemap Generator reads your files. Some common encodings are:
		</p>
				<ul>
				<li><strong>encoding="utf-8"</strong> is the assumed default
				</li><li><strong>encoding="ascii</strong>" is a subset of UTF-8 so you don't have to specify it
				</li><li><strong>encoding="iso-8859-1</strong>" is common for many west European languages
				</li></ul>
		  </font>
		  
		  <table border="0" cellpadding="2" cellspacing="0" width="100%"> 
				<tbody><tr> 
				<td style="border-top: 1px solid rgb(221, 173, 8); background-color: rgb(254, 250, 222);"><a name="creating_mobile" id="creating_mobile"></a><b>2b. Additional information for creating a mobile configuration file</b></td> 
				</tr> 
			</tbody></table>
				<p><font size="-1">You create a configuration file for a Mobile Sitemap in the same way as for a non-mobile Sitemap. However, you must create a separate config file for each markup language and run the Sitemap Generator with each config file separately so that you create a separate Sitemap for each.</font></p>
				<p><font size="-1">Each config file must:</font></p>
		  <ul>
		    <li><font size="-1">Specify a different filename for the <a href="#create_config"><strong>store_into</strong> value</a>.</font></li>
	        <li><font size="-1">Use <a href="#filter_examples">filters</a> to specify the URLs to exclude and include for the markup language. Remember that each Sitemap should include URLs for only one markup language. This means that the same URL may be included in multiple Sitemaps, if those URLs serve multiple markup languages.</font></li>
	      </ul>
			<p><strong><font size="-1">Examples of filtering</font></strong></p>
			<p><font size="-1">Below are some examples of how you can use extension-based filters to generate Mobile Sitemaps for different markup languages. The specific filtering you use should be based on the types of markup languages used in your site, and how you specify each type. If you have implemented the details of your site differently (for instance, you may organize URLs with different markup languages in separate folders), you should filter based on the specifics of your site implementation. Remember that filters are applied in the order you list them in the config file. So, the first filter you should list is a &quot;pass&quot; action that specifies the URLs you want to include in the Sitemap. </font></p>
			<p><font size="-1">To create a Sitemap for WML (WAP 1.2) content:</font></p>
			
			<pre>&lt;filter action="pass" type="wildcard" pattern="*.wml" /&gt;
&lt;filter action="drop" type="wildcard" pattern="*.*" /&gt;<br>
</pre>
			
			<p><font size=-1>To create a Sitemap for XHTML mobile profile (WAP 2.0) content:</font></p>
			
			<pre>&lt;filter action="pass" type="wildcard" pattern="*.xhtml" /&gt;
&lt;filter action="drop" type="wildcard" pattern="*.*" /&gt;<br>
			</pre>
			<table border="0" cellpadding="2" cellspacing="0" width="100%"> 
				<tbody><tr> 
				<td style="border-top: 1px solid rgb(221, 173, 8); background-color: rgb(254, 250, 222);"><a name="copy"></a><b>3. Uploading the files to your web server</b></td> 
				</tr> 
			</tbody></table>
		<p><font size="-1"> You should upload the following files to your web server in a location you can access from a command line: </font></p>
			
			<font size="-1"><ul>
              <li><strong> config.xml</strong> &#8212;this is the configuration file you just created using <strong>example_config.xml</strong>. </li>
              <li><strong> sitemap_gen.py</strong> &#8212;this is the Python script that generates your Sitemap. </li>
              <li><strong> urllist.txt</strong> &#8212;this file is optional; you only need to include it if you used the text file method of generating a Sitemap. </li>
		  </ul>
			
		  </font>
		  <p><font size="-1"> The method you use to upload these files depends on your environment. Common methods include <a href="http://www.google.com/search?q=ftp">FTP</a> and SCP. For more information, contact your web host.		  </font></p>
			
			<table border="0" cellpadding="2" cellspacing="0" width="100%"> 
				<tbody><tr> 
				<td style="border-top: 1px solid rgb(221, 173, 8); background-color: rgb(254, 250, 222);"><a name="execute"></a><strong>4. Running the Sitemap Generator script (sitemap_gen.py) </strong></td> 
				</tr> 
			</tbody></table>
				
				<p><font size="-1">
In order to run the Sitemap Generator, you&#8217;ll need to connect to your
web server. The method you use to connect depends on your environment.
For instance, you can generally access a UNIX-based server using <a href="http://www.google.com/search?q=ssh">SSH</a>.  For more information on connecting to your web server and running scripts, talk to your web host. </font></p>
				
				<p><font size="-1"> Once you have copied the files to your web server, you'll need to run the Sitemap Generator script. 
				Connect to your web server and run the following command (replace <strong>&lt;path/config.xml&gt;</strong>
with the path to and filename of your configuration file; if you have
uploaded this file to the same location as the Python script, you can
exclude the path):</font></p>
				
				<pre>python sitemap_gen.py --config=&lt;path/config.xml&gt;
</pre>
<p><font size="-1">For instance, a UNIX-based command line might look similar to this:</font></p>
<p><img src="images/python_command.gif" alt="Python command"></p>
<p><font size="-1">A MS-DOS-based command shell might look similar to this:</font></p>
<p><img src="images/python_dos.gif" alt="Python command"></p>
<p><font size="-1"><b>Tip:</b> If you're testing your configuration and are not ready to submit your Sitemap, 
				  the following syntax will prevent Sitemap Generator from contacting Google:</font></p>
				<pre><br>	$ python sitemap_gen.py --config=config.xml --testing</pre>
				<font size="-1"><p>You'll see the status of your request in the command prompt:</p></font>
<pre>	
	Reading configuration file: /path/config.xml
	Opened URLLIST "/path/urllist.txt"
	Walking DIRECTORY "/var/www/html/dir"
	Walking DIRECTORY "/var/www/html/dir2"
	Opened ACCESSLOG "/etc/httpd/logs/access-0.log"
	Sorting and normalizing collected URLs.
	Writing Sitemap file "/path/sitemap.xml.gz" with 1092 URLs
	Notifying search engines.
	Notifying www.google.com
	Count of file extensions on URLs:
		208  .html
		574  .jpg
		...
		Number of errors: 0
		Number of warnings: 0</pre>
				<font size="-1">
				<p>If you don't see very much output like this, remember that the verbose setting in your configuration file 
				affects how much information is printed on the screen.  This example is representative of setting verbose to "1".</p>
				<p>Any errors in the file will also be returned.  For instance, if you leave the url= attribute off a 
				directory entry, the script will output the following:
				</p></font>
<pre>	
	[ERROR] Directory entries must have both "path" and "url" attributes
	Number of errors: 1</pre>
				<font size="-1">
				</font>
				<p><font size="-1">Correct any errors in your <b>config.xml</b> file and re-run the script. If no errors are present, 
				the Sitemap Generator will create a new <b>sitemap.xml.gz</b> file in the location you specified in the config file. </font></p>
				<table border="0" cellpadding="2" cellspacing="0" width="100%"> 
				<tbody><tr> 
				<td style="border-top: 1px solid rgb(221, 173, 8); background-color: rgb(254, 250, 222);"><a name="submitting" id="submitting"></a><strong>5. Submitting your Sitemap to Google </strong></td> 
				</tr> 
			</tbody></table>
				<p><font size="-1">The Sitemap Generator creates a <strong>sitemap.xml.gz</strong>
file in the location you specified in the config file. Once this file
is successfully created, make sure it is accessible through a web
browser. Then, <a href="http://www.google.com/support/webmasters/bin/answer.py?answer=34575&topic=8496">add</a>  it to your <a href="https://www.google.com/webmasters/sitemaps/siteoverview">Google Sitemaps</a> account.
This enables Google to provide you with useful status and statistical
information. If Google reports problems with your Sitemap, you can
correct the problems and resubmit it. You
only have to add the Sitemap manually once. After that, you can use
an <a href=submit.html#ping>HTTP request</a> to notify Google about changes to your Sitemap (although you can also resubmit it through your Google webmaster tools account). </font></p>
		        
				<table border="0" cellpadding="2" cellspacing="0" width="100%"> 
				<tbody><tr> 
				<td style="border-top: 1px solid rgb(221, 173, 8); background-color: rgb(254, 250, 222);"><a name="recur"></a><b>6. Setting up a recurring script</b></td> 
				</tr> 
		  </tbody></table>
		  <font size="-1">
				<p>We suggest setting up Sitemap Generator to run as often as your content is changed, to a maximum frequency of once per hour.</p>
		  </font>
		  <p><font size="-1">Webmasters with a UNIX web server may consider setting this up as a <a href="http://www.google.com/search?q=cron">cron job</a>. </font></p>
				<font size="-1"><p>Webmasters using other platforms should contact their system administrator for help in configuring recurring scripts. 
				You may also benefit from peer advice in the Google Sitemaps Group on <a href="http://groups.google.com/group/Google_Webmaster_Help-Sitemap?tsc=1">Google Groups</a>.
</p>
				
	      </font>
				<p><font size="-1"> You can use an <a href=submit.html#ping>HTTP request</a> to let Google know about changes to your Sitemap. However, please make sure that you log in to <a href="https://www.google.com/webmasters/tools/siteoverview">Google Webmaster Tools</a> with your Google Account once to manually <a href=http://www.google.com/support/webmasters/bin/answer.py?answer=34575&topic=8496>add your Sitemap</a> to your Google Webmaster Tools account.</font></p>
				<font size="-1"></font>		
			    <table border="0" cellpadding="2" cellspacing="0" width="100%"> 
				<tbody><tr> 
				<td style="border-top: 1px solid rgb(221, 173, 8); background-color: rgb(254, 250, 222);"><a name="troubleshoot"></a><b>Troubleshooting</b></td> 
				</tr> 
			</tbody></table>
				<font size="-1">
				<p>In this section we talk about some common questions or issues that some people run into while using Sitemap Generator, 
				and what you can do if you come across one of these.</p>
				<p><b>Web-accessible</b></p>
				<p><b>Issue:</b> Sitemap Generator returns the following error and warning:</p>
				</font>
<pre>	
	[ERROR] When attempting to access your generated Sitemap at the following URL:
	http://www.example.com/sitemap.xml.gz
	we failed to read it.  Please verify the store_into path you specified in
	your configuration file is web-accessible.  Consult the FAQ for more
	information.
	[WARNING] Proceeding to notify with an unverifiable URL.</pre>
				<font size="-1">
				<p><b>What just happened?</b> Sitemap Generator created the file where you specified, then attempted to retrieve it using 
				HTTP just as a search engine would, and failed.  It went ahead and notified search engines anyway, but it's 
				outputting the error and warning to let you know that your Sitemap may be not readable by search engines.</p>
				<p>Sitemap Generator creates your Sitemap file at the path specified in the store_into attribute of your <b>config.xml</b> file. 
				Sitemap Generator then builds a URL to that file using the base_url attribute, and reports the URL to search engines.  
				For instance, if you set the configuration to:</p>
				</font>
<pre>	&lt;site base_url="http://www.example.com/"
	      store_into="/var/www/html/sitemap.xml.gz"&gt;</pre>
				<font size="-1">
				</font><p><font size="-1">Sitemap Generator will notify search engines to look for your Sitemap at:</font></p>
				
				<pre>	http://www.example.com/sitemap.xml.gz</pre>
				<font size="-1"><p>
				The file must be accessible through this URL.  If the file can not be retrieved using this URL, search engines have 
				no way of finding your Sitemap.</p>
				</font><p><font size="-1"><b>What can you do?</b>  You need to verify that your <b>config.xml</b> is specifying the correct base_url and 
				store_into paths for your Sitemap.  You also need to confirm that web browsers can retrieve the Sitemap file off 
				of the base_url.  If you find errors in the path or URL, you may need to re-run Sitemap Generator, or just move 
				the Sitemap file to the correct place and notify search engines manually through their web sites.
				</font></p>
				<font size="-1"><p><b>Support for XML</b></p>
				<p><strong>Issue:</strong> Sitemap Generator gives the following error:</p>
				</font>
<pre>	
	Some installs of Python 2.2 do not include complete support for XML. 
	Please try upgrading your version of Python and re-running the script.</pre>
				<font size="-1"><p>
				<b>What just happened?</b>  As the message says, some platforms have a version of Python (the language the 
				Sitemap Generator script is written in) that is missing support libraries needed for processing XML files.  
				This script requires full XML support in order to run.
				</p>
				<p><b>What can you do?</b> Try upgrading your installed version of Python to a newer version.  
				You will probably need to contact your system administrator to do this.</p>
				<p>Note that this just affects the Sitemap Generator, not Sitemaps overall.  If you have another method or tool 
				for creating Sitemaps, you can certainly use it and submit your Sitemaps to search engines.</p>
				<p><b>What are all the extra files in the .gz or .zip?</b></p>
				<p>When you extract the sitemap_gen.py script, you'll probably see quite a few more files than we refer to above.  
				The full file list looks closer to this:</p>
				</font>
	<pre>	
	AUTHORS
	ChangeLog
	COPYING
	example_config.xml
	example_urllist.txt
	PKG-INFO
	README
	setup.py
	sitemap_gen.py
	test_sitemap_gen.py</pre>
		  <font size="-1"><p>
				The extra files tend to be information on the package and licensing terms.  
				You are encouraged to look through these files.</p>
				<p>The one exception is test_sitemap_gen.py, which is a unit-test script that other developers may find useful 
				if they wish to contribute to this open source project.  If you intend to use Sitemap Generator without 
				modifying any of the source code - this is the expected case for nearly everyone - you probably don't need this test script.
</p>
	  If you are interested in helping with this project, please visit <a href="http://code.google.com/p/sitemap-generators/wiki/Contributing">the contributor wiki page</a>.</p>
	  
	  <font size="-1"></font></font>
		  <p><font size="-1"><b><a name="nonascii"></a>Non-ASCII characters </b></font></p>
				<font size="-1"><font size="-1">
				</font></font>
				<p><font size="-1"><strong>Issue:</strong> Your site domain name or URLs within it contain non-ASCII characters.</font></p>
				<p><font size="-1">Generally, non-ASCII URLs should be <a href="protocol.html#escaped">encoded using UTF-8</a> before being percent-escaped. However, some webservers only respond correctly if URLs are encoded using an encoding other than UTF-8. All URLs within your Sitemap, as well as the URL of the Sitemap itself must be encoded for readability by the web server on which they are located. Within the <a href="#sitetag">site definition section</a>, use the optional <strong>default_encoding</strong> attribute to specify the encoding used by your webserver. If you don't use this tag and your webserver uses an encoding other than UTF-8, we can't know which encoding to use.</font></p>
				<p><font size="-1">If your URLs contain non-ASCII characters, we recommend that you run the Sitemap Generator script using Python 2.3 or higher. This version of Python has increased non-ASCII support. If your domain name contains non-ASCII characters, you must use Python 2.3 or later, as Internationalizing Domain Names in Applications (IDNA) support wasn't added until this version. Without IDNA support, the Sitemap Generator can't correctly encode a non-ASCII domain name. </font></p>
				<font size="-1">
	  
	  
	  
	<br>
	<p class="d" align="right"><i>Last modified: 15 April 2006</i></p>
	  </font></div>
	</td> 
  </tr> 
  <tr> 
    <td width=1% valign=top><img src=http://www.google.com/images/art.gif width=143 height=53 vspace=5 hspace=15></td> 
    <td style="background-color: #ffffff" width=1 valign=top><img src=http://www.google.com/images/cleardot.gif width=1 height=1></td> 
    <td style="background-color: #ffffff" width=10 valign=top><img src=http://www.google.com/images/cleardot.gif width=1 height=1></td> 
    <td valign=middle><div class=footer> 
        <div align=center><font size="-1"> &copy;2007 Google - <a href=http://www.google.com/privacy.html>Privacy Policy</a> - 
		<a href=http://www.google.com/accounts/TOS>Terms and Conditions</a> - <a href=http://www.google.com/about.html>About Google</a> </font></div> 
      </div></td> 
  </tr> 
</table> 
</body>
</html>

